You are here: Building the Model: General Elements > Locations > Location Downtimes > Special Notes Regarding Location Downtimes
1. When an entity preempts another entity (Example 1), or when an entity preempts a downtime (Example 2), or when a downtime preempts an entity (Example 3), any resources owned by the preempted entity or downtime will be freed temporarily until the preempting entity or downtime finishes at the location. At that time, the original entity or downtime will seek to claim the exact units of the resource or resources it owned before the preemption occurred.
2. As shown in examples 5 and 6, an entity that requires a location setup will be treated differently depending on the preempting activity. If the preempting activity is another entity, the current setup in process will have to start over from the beginning. However, if the preempting activity is a downtime, the remaining setup time will finish upon completion of the preempting downtime.
3. Locations will not go down if they are in a blocked state. A location is blocked if it has an entity that cannot be routed because of the unavailability of the next location. This may also include the time an entity waits to enter a location based on a routing condition, such as LOAD.
4. Locations will not go down if any of the occupying entities are waiting for a resource or are waiting at any downtime inhibiting statement.
Downtime inhibiting statements
5. In cases where a downtime or other entity attempts to preempt an entity’s use of a location, a preemption process may be defined to override the default way of handling the preemption. See Preemption Process Logic.